System files must be monitored for unauthorized changes.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-224840	WN16-00-000240	SV-224840r891691_rule		Medium

Description
Monitoring system files for changes against a baseline on a regular basis may help detect the possible introduction of malicious code on a system.

STIG	Date
Microsoft Windows Server 2016 Security Technical Implementation Guide	2023-03-02

Details

Check Text ( C-26531r891691_chk )
Determine if the system is monitored for unauthorized changes to system files (e.g., .exe, .bat, .com, .cmd, and *.dll) against a baseline on a weekly basis. If system files are not being monitored for unauthorized changes, this is a finding. An approved and properly configured solution will contain both a list of baselines that includes all system file locations and a file comparison task that is scheduled to run at least weekly.

Check Text ( C-26531r891691_chk )

Determine if the system is monitored for unauthorized changes to system files (e.g., *.exe, *.bat, *.com, *.cmd, and *.dll) against a baseline on a weekly basis.

If system files are not being monitored for unauthorized changes, this is a finding.

An approved and properly configured solution will contain both a list of baselines that includes all system file locations and a file comparison task that is scheduled to run at least weekly.

Fix Text (F-26519r465423_fix)
Monitor the system for unauthorized changes to system files (e.g., .exe, .bat, .com, .cmd, and *.dll) against a baseline on a weekly basis. This can be done with the use of various monitoring tools.